EntelligenceAI PR Summary

Upgrades @davidzemon/passport-okta-oauth from 0.0.5 to 0.0.7 and synchronizes the lockfile with all resulting dependency changes.

• plugins/auth-backend/package.json: Version range updated from ^0.0.5 to ^0.0.7
• yarn.lock: Direct upgrade of @davidzemon/passport-okta-oauth to 0.0.7
• yarn.lock: Pins @backstage/plugin-gitops-profiles transitive deps to fixed older versions (@backstage/config 0.1.1, @backstage/core-components 0.1.0, @backstage/core-plugin-api 0.1.0, @backstage/theme 0.1.1)
• yarn.lock: Pins @backstage/core-plugin-api workspace deps to fixed versions (@backstage/config 0.1.1, @backstage/version-bridge 0.1.0)
• yarn.lock: Upgrades transitive deps: cross-fetch, node-fetch, core-js, dompurify, domutils, entities, @types/unist, react-syntax-highlighter, prismjs
• yarn.lock: Introduces new transitive resolutions for pinned legacy Backstage packages (older react-markdown, unified, material-table ecosystem, react-hook-form v6, d3-* v2, vfile v4, etc.)

Confidence Score: 4/5 - Mostly Safe

Likely safe but review recommended — this PR upgrades @davidzemon/passport-okta-oauth from 0.0.5 to 0.0.7 in plugins/auth-backend/package.json, which is a minor version bump for an authentication library at a very early semantic version (0.0.x), meaning breaking changes are possible without semver guarantees. The yarn.lock changes also pin transitive dependencies for @backstage/plugin-gitops-profiles to older fixed versions, which warrants a manual check to confirm these pinned versions don't introduce incompatibilities or known vulnerabilities. No automated review comments were generated and the change is straightforward, but the nature of an auth library upgrade at 0.0.x deserves a quick human review of the changelog.

Key Findings:

• The @davidzemon/passport-okta-oauth package is at version 0.0.x, where semver patch/minor guarantees don't apply — jumping from 0.0.5 to 0.0.7 in an auth library could silently introduce behavioral changes in the Okta OAuth flow without a major version bump.
• The yarn.lock pins @backstage/config at 0.1.1, @backstage/core-components at 0.1.0, and @backstage/core-plugin-api at 0.1.0 as transitive dependencies — these are very early versions and should be verified that they don't conflict with the broader Backstage version in use.
• No security advisories or logic issues were flagged by automated review, and the scope of change is limited to plugins/auth-backend/package.json and yarn.lock, which are the expected files for a dependency upgrade.

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react@​17.0.2
	typescript@​4.7.4
	swc-loader@​0.2.3
	storybook-dark-mode@​1.1.2
	react-hot-loader@​4.13.1
	react-dom@​17.0.2

View full report

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm polished under OFL-1.1 License: OFL-1.1 - The applicable license policy does not permit this license (5) (package/docs/assets/fonts/LICENSE.txt) From: ? → npm/@storybook/addon-actions@6.5.16 → npm/polished@4.2.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/polished@4.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm typescript under W3C-20150513 License: W3C-20150513 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) From: storybook/package.json → npm/typescript@4.7.4 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.7.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!